Skip to content

Conversation

@jeffhandley
Copy link
Member

Port of #84432 to release/7.0-staging per tactics approval of the 6.0 fix. Performed with a clean cherry-pick of 36a721a from stephentoub:fixsocketreordering.

There are a couple of places where we read the _continuation field and then read some other state which we assume to be consistent with the value we read in _continuation.  But without a fence, those secondary reads could be reordered with respect to the first.
@jeffhandley jeffhandley added Servicing-consider Issue for next servicing release review area-System.Net.Sockets labels Apr 11, 2023
@jeffhandley jeffhandley added this to the 7.0.x milestone Apr 11, 2023
@jeffhandley jeffhandley requested a review from stephentoub April 11, 2023 17:47
@ghost
Copy link

ghost commented Apr 11, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Port of #84432 to release/7.0-staging per tactics approval of the 6.0 fix. Performed with a clean cherry-pick of 36a721a from stephentoub:fixsocketreordering.

Author: jeffhandley
Assignees: jeffhandley, stephentoub
Labels:

Servicing-consider, area-System.Net.Sockets

Milestone: 7.0.x

@jeffhandley
Copy link
Member Author

@stephentoub beat me to it with #84641.

@jeffhandley jeffhandley deleted the fixsocketreordering-7.0 branch April 11, 2023 17:51
@ghost ghost locked as resolved and limited conversation to collaborators May 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-System.Net.Sockets Servicing-consider Issue for next servicing release review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants